Setting up NFS Services Getting Started Guide 181 will allow anyone (originating from any hostname) to have read-only access to the /mnt/cdrom directory. This line /opt/wordperfect *.company.com(rw) Allows any users coming from a hostname within the .company.com domain to access the /opt/wordperfect directory, with read-write access (dangerous, but per- haps necessary to run the application). The clients can then mount the NFS resource on your OpenLinux system with a command like this one (or equivalent commands or graphical interfaces on their systems): $ mount -t nfs linuxhostname:/opt/wordperfect/ /applications/wordperfect NOTE: If you have enabled NFS as a start-up daemon, you can use the following procedure to start NFS immediately (without rebooting). To re-start NFS services (so that configuration changes take effect), enter these two commands at a command prompt (while logged in as root): # /etc/ rc.d/init.d/nfs stop # /etc/ rc.d/init.d/nfs start The new configuration is loaded and NFS is running. CAUTION: NFS mounting involves several security options; the username provided by the client and the access level granted in the /etc/exports file are only two considerations when setting up an NFS server intended for use by numerous clients. See the man pages references below for details on the /etc/exports settings. All the required NFS daemons are started at boot time by default. The portmap- per which controls access to NFS services, however, utilizes the /etc/hosts.allow and /etc/hosts.deny files for access control. To enable other machines to mount a directory from your system via NFS, you must add a line to /etc/hosts.allow for each machine or domain which you wish to allow to connect to the portmapper. In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name, nor will it try to match NIS netgroups. Thus only network number patterns (IP addresses) will work for portmap access control.